home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
bbsutil
/
ticsf100.zip
/
TICTOSS.DOC
< prev
next >
Wrap
Text File
|
1994-05-25
|
10KB
|
331 lines
TicToss for Spitfire
Release 1.00
May 25, 1994
(c) Copyright 1994 WER Development, All Rights Reserved
WER Development
500 Roselawn, Suite 4
Monroe, LA 71201
BBS: (318) 325-6608 (v.32bis/V.FC 28.8)
Fidonet: WerDev@Fidonet#1:136/1.0
Internet: WerDev@Aol.Com
Fax: (318) 387-1805
WHAT IS TICTOSS FOR SPITFIRE?
TicToss allows Spitfire sysops to participate in File Distribution
Networks (commonly referred to as FDNs or simply File Echos).
File Distribution Networks distribute software in archived form
and distribute TIC files with the archive that contains
information about the archive. TicToss processes the TIC files so
the archives are copied to the proper download path for BBS
callers, and imports descriptions for the archives into your
SFFILES.BBS.
TicToss for Spitfire Page 1
COPYRIGHT AND LICENSE
TicToss for Spitfire is (C) Copyright 1994 WER Development, All
Rights Reserved.
TicToss for Spitfire is a fully functional shareware package.
After a reasonable evaluation period to ensure it meets your
needs, you are obligated to register the application with WER
Development by completing the ORDER.FRM and returning it to WER
Development.
WARRANTY
No warranty of any kind is offered on TicToss for Spitfire.
Furthermore, you use this program AT YOUR OWN RISK. Under no
circumstances shall the author be liable for damage this software
may inflict upon you or your property -- either by itself or with
your help.
SNAPSHOT of KEY FEATURES OF TICTOSS FOR SPITFIRE
* Elegantly wraps the description text without truncation
* Supports using TICK for Hubbing Files
* Supports Planet Connect Downlinks
* Supports ftp.fidonet.org Downlinks
LIMITATIONS OF TICTOSS FOR SPITFIRE
* Maximum of 150 different AreaNames/File Echos currently
* Maximum of 4 lines of extended description currently
SOFTWARE REQUIREMENTS
TicToss for Spitfire has been tested with Spitfire 3.4.
Additional versions of TicToss are being developed for other BBS
packages. Currently we have versions for FeatherNet Pro, RBBS-PC,
and TriBBS under development.
TicToss for Spitfire is currently a DOS only application. TicToss
has been tested under DESQview 2.4x as well as OS/2 2.1's DOS
support.
ACKNOWLEDGEMENTS
Barry Geller, author of the TICK package.
TicToss for Spitfire Page 2
TICTOSS.CFG INSTALLATION
TicToss compiles its TICTOSS.CFG before processing new arrived
files and their TICs. TicToss's configuration file works off the
keyword concept currently used by most Fidonet related utilities.
A sample TICTOSS.CFG should be present in our distribution archive
with much of its information duplicated from this section of our
documentation.
First, TicToss needs to know where to expect to find the TICs &
the archived files that arrive from your Fidonet Host. The
"Inbound" keyword should be set to the path where TicToss will
find the arriving TICs and Files. For BinkleyTerm users this will
be the setting you have for "NetFile", "KnownInbound", or
"ProtInbound" depending on your configuration. For FrontDoor
users this will be the FILES directory.
(We STRONGLY suggest the usage of session level passwords with
your mailer to prevent someone trying to send you files which you
do not expect. Session Level Passwords are a feature of your
mailer -- refer to your mailer's security section for help in
setting up.)
TicToss currently supports only ONE "Inbound" directory.
Example: Inbound d:\binkley\inboundp
Next, TicToss needs information about how it should process the
TIC files. The "AreaName" is the name each File Distribution
Network uses for its various File Echos. The AreaName should be
unique for each file echo. TicToss currently supports the
commonly used limitation of 8 CHARACTERS for the AreaName. There
should not be any spaces as part of the AreaName -- underline
characters are substituted. (ie RBBS UTL would be RBBS_UTL)
TicToss currently supports up to 150 AreaNames which translates
into 150 different File Echos.
Example: AreaName UTILNET
The "FilePath" is the full path where TicToss will copy the files
after their TIC information has been verified as valid &
description added to your SFFILES.BBS. (After copying the file,
TicToss deletes the file in your Inbound directory.)
Example: FilePath D:\FileBone\Utility
TicToss for Spitfire Page 3
The "SFFile" is the file where the File descriptions will be
written. There should be a SFFILES.BBS in each of Spitfire's file
directories, and these should all be setup prior to using TicToss.
Example: SFFile D:\Spitfire\SFFiles.BBS
The "Host" is the Fidonet address of the system which sends the
files and their associated TIC file. As far as we know the Host's
address is specified in the 3D form of Zone:Network/Node, but
there isn't any manipulation done on TicToss's part to break an
address apart -- TicToss just compares the string of characters
for a proper match when verifing TIC files. If you find yourself
on the receiving end of a different address format, just note the
format and use it instead. We would also appreciate hearing about
this variation to help alert others.
Note: The Host keyword works in conjunction with the Password
keyword.
Example: Host 1:136/2
The "Password" is the password your Host adds to the TIC file
before forwarding the TIC and its file to your system. This
password is generally agreed upon by mutual consent, but if your
Host assigned your password at random, you may have to do a bit of
detective work. Using a text file browser (such as LIST), look at
the very last line of the TIC file. The last line should begin
with "Pw" which is short for Password -- the word that follows
"Pw" is the Password for AreaName. Most sysops receive files from
only one system, but since each Password is associated with an
AreaName you may receive different file echos from different Hosts
if you so desire. Just remember to use a UNIQUE and DIFFERENT
Password for each system sending you Files.
Note: The Password keyword works in conjunction with the Host
keyword.
Example: Password LetMeIn
TicToss for Spitfire Page 4
TICTOSS.CFG INSTALLATION (Optional Parameters)
In addition to the above required configuration information for
your TICTOSS.CFG, there are a couple of optional keywords which
may be of use to some TicToss users.
The "Preprocess" keyword is a temporary work around for those who
need support for hubbing of files (which will be included in a
future release). Using "Preprocess" allo